Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat: Support auto revisions (#422) #422

Merged
merged 3 commits into from
Nov 7, 2024
Merged

feat: Support auto revisions (#422) #422

merged 3 commits into from
Nov 7, 2024

Conversation

palmerj
Copy link
Contributor

@palmerj palmerj commented Feb 27, 2024

Checklist

  • Update local tags using git fetch --tags.
  • Check git tag --sort=version:refname for the latest released version.
  • Depending on whether this is a major (X+1.0.0), minor (X.Y+1.0), or patch (X.Y.Z+1) release:
    • If this is a major or minor release, create a release-X.Y branch.
    • If this is a patch release, check out the existing release-X.Y branch.
  • Add a change log entry to CHANGELOG.md.
  • Look for anywhere there is a list of version numbers, such as the Makefile, test files, or others. In all those places, add your new version.
  • Finish any other changes on this branch, such as merging in origin/master.
  • Push the branch.
  • Create a pull request for the branch.
  • Wait for the pull request to build.
  • Tag the final commit on the branch with X.Y.Z, for example, 1.10.2.
  • git push origin TAG with the tag created above.
  • Wait for the tag job to finish and the package to appear in the test repository (replace X.Y.Z with the tag in the links).
  • Manually promote the package repository to the "prod" repository.
  • Manually trigger the PR pipeline to work around a GitHub limitation
  • Wait for the pull request to build and merge it.

@palmerj palmerj changed the title feat: Support auto revisions feat: Support auto revisions (#422) Feb 27, 2024
@palmerj palmerj force-pushed the txn_revision_id branch 3 times, most recently from 3952e52 to bf6c811 Compare February 27, 2024 10:23
@palmerj palmerj merged commit 1fe9a72 into master Nov 7, 2024
36 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

1 participant